-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Address input bugs #122
base: beta
Are you sure you want to change the base?
Address input bugs #122
Conversation
Reviewer's Guide by SourceryThis PR addresses input validation and terminology consistency issues. The main changes include updating the input validation logic to properly handle programmatic resets and replacing deprecated 'numeric' type references with the standard 'number' type. The implementation also includes UI improvements for bordered inputs and label positioning. Class diagram for BaseInput and AuroFormValidation changesclassDiagram
class BaseInput {
- String max
- String min
- String inputMode
+ handleInput()
}
class AuroFormValidation {
+ validateType(elem)
+ validateAttributes(elem)
+ handleInputReset(elem)
}
note for BaseInput "Changed inputMode from 'numeric' to 'number'"
note for AuroFormValidation "Added logic to reset validity state on programmatic reset"
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
70bff16
to
0caba7e
Compare
e96a7eb
to
480c4e1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also, the disabled state colors are off from https://www.figma.com/design/VpUz89Ov6ImBpY5YvzYbZW/Auro-toolkit?node-id=3264-27509&m=dev (not sure if this is the latest design)
@@ -144,6 +148,9 @@ export default class AuroFormValidation { | |||
this.validateType(elem); | |||
this.validateAttributes(elem); | |||
} | |||
} else if (elem.value === undefined) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
validationShouldRun
is false, but why do we touch validity?- maybe
validationShouldRun
should be fixed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are touching validity to reset it. In the case of this fix, users expect that validity state to reset when setting the element to value=undefined
. Since validationShouldRun
is false, it skips the validation logic and resets the validity state.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we not reset the validity always at the beginning of the validate function? as elem.value
is not only case that we want to reset.
Per this design spec, the disabled colors are correct: The design spec linked in the previous comment is outdated. |
ab0c7a0
to
8845302
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
2ccdf41
to
8845302
Compare
85d413a
to
4177a17
Compare
54eb955
to
9a2ad3f
Compare
Alaska Airlines Pull Request
Before Submitting this pull request:
Development
sectionnote: all pull requests require at least one linked ticket
Ready For Review
, all ticket's linked underDevelopment
must have their status changed toReady For Review
as wellBy submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I have performed a self-review of my own update.
Summary by Sourcery
Fix input type inconsistencies by changing 'numeric' to 'number' in both code and documentation, enhancing clarity and compliance with HTML standards.
Bug Fixes:
Enhancements:
Documentation: